Unified identification verification system

ABSTRACT

A system includes a processor of an ID verification node connected to at least one web server node over a network and a memory on which are stored machine-readable instructions that when executed by the processor, cause the processor of the ID verification node connected to at least one node over a network; a memory on which are stored machine-readable instructions that when executed by the processor, cause the processor to: acquire verifiable ID scan image data of all users within a country of residence; receive users&#39; profile data; generate encrypted user profile attributes comprising DNA; execute a transaction to store the encrypted user profiles on a ledger along with corresponding access policies; and generate an intermediate representation for each user based on the verifiable ID scan image data and the encrypted user profile attributes.

TECHNICAL FIELD

This present disclosure generally relates to security systems, and moreparticularly, to verification of identity of users, IoT devices, etc.

RELATED APPLICATIONS

This application is a Continuation-In-Part of U.S. application Ser. No.16/697,157 filed Nov. 26, 2019, which issued on Jun. 21, 2022 as U.S.Pat. No. 11,367,065 titled “Distributed Ledger System for ElectronicTransactions”; which is a continuation of U.S. application Ser. No.16/393,956 filed on Apr. 24, 2019, which issued as U.S. Pat. No.10,999,276 titled “Industrial Internet Encryption System”; Patent '065is also a continuation of U.S. application Ser. No. 15/875,378 filed onJan. 19, 2018, which issued as U.S. Pat. No. 10,911,217 titled“Endpoint-to-Endpoint Cryptographic System for Mobile and IoT Devices”;Patent '276 is also claims priority to U.S. Non-Provisional applicationSer. No. 13/364,339 filed Feb. 2, 2012, which are hereby incorporated byreference herein in its entirety.

It is intended that each of the referenced applications may beapplicable to the concepts and embodiments disclosed herein, even ifsuch concepts and embodiments are disclosed in the referencedapplications with different limitations and configurations and describedusing different examples and terminology.

BACKGROUND

A typical identification (ID) card includes information about thecardholder such as name, address, a physical description, and picture.Most ID cards also contain some sort of machine-readable identifier suchas a magnetic stripe, a bar-code, QR code, a smart chip, etc. The IDcards are typically used to restrict access for unauthorizedcardholders. For example, laws in every state require a person to be atleast a minimum age to purchase alcohol or tobacco products. Similarly,in most states, a patron must be at least a minimum age to enter a bar.Typically, to verify that a person meets age requirements, the personmust present an ID card prior to purchasing products or prior to beingadmitted to an establishment having age requirements.

There are numerous problems with using ID cards for the purposesmentioned above. One problem relates to fake or altered ID cards. It isvery common for under age people to obtain fake or altered ID cards thatshow that the cardholder meets a minimum age requirement. In addition,it is common for under age people to use a valid ID card belonging tosomeone else. The quality of many fake or altered ID cards is such thatit is extremely difficult to distinguish or determine the validity of anID card.

Another problem relating to the ID cards is that it is cumbersome toverify their authenticity. For example, when a law-enforcement officerverifies the validity of an ID card, the officer typically gets on aradio and reads the ID number to a remote person who has the ability toverify the validity of the ID. This procedure is labor intensive andtime-consuming for the officer. These verification procedures may resultin false positive or negative identifications.

The existing solution do not allow for verification of a person's namefrom an ID and vice versa—verification of the ID from the name itself.The conventional verification systems do not provide for an intermediaterepresentation (QR code or any other string that connect the verifiablecredential to the person) that may be used to check the name of personto verify if it is real.

Accordingly, an efficient and accurate system for verification ofidentity of users, IoT devices, supply chain of electronics, etc. isdesired.

SUMMARY

One embodiment provides a processor and memory of an ID verificationnode configured to acquire verifiable ID scan image data of all userswithin a country of residence; receive users' profile data; generateencrypted user profile attributes including DNA; execute a transactionto store the encrypted user profiles on a ledger along withcorresponding access policies; and generate an intermediaterepresentation for each user based on the verifiable ID scan image dataand the encrypted user profile attributes.

Another embodiment provides a method that includes one or more ofacquiring verifiable ID scan image data of all users within a country ofresidence; receiving users' profile data; generating encrypted userprofile attributes including DNA; executing a transaction to store theencrypted user profiles on a ledger along with corresponding accesspolicies; and generating an intermediate representation for each userbased on the verifiable ID scan image data and the encrypted userprofile attributes.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a network diagram of a system 100 including an IDverification server node and nodes that require ID verification,according to disclosed embodiments.

FIG. 2 illustrates a Universal Identification Verification System(UIVS), in accordance with embodiments of the present invention.

FIG. 2A illustrates a user interface for providing data to the UniversalIdentification Verification System (UIVS), in accordance withembodiments of the present invention.

FIG. 3 illustrates an example network including details of the IDverification server node, in accordance with embodiments of the presentinvention.

FIG. 4A illustrates a flow diagram of an example method, in accordancewith embodiments of the present invention.

FIG. 4B illustrates a network used for the Universal IdentificationVerification System including an AI module, in accordance withembodiments of the present invention.

FIG. 5 illustrates an example computer system/server node, which mayrepresent or be integrated in any of the components of the embodimentsof the present invention.

DETAILED DESCRIPTION

It will be readily understood that the instant components, as generallydescribed and illustrated in the figures herein, may be arranged anddesigned in a wide variety of different configurations. Thus, thefollowing detailed description of the embodiments of at least one of amethod, apparatus, non-transitory computer readable medium and system,as represented in the attached figures, is not intended to limit thescope of the present disclosure as claimed but is merely representativeof selected embodiments.

The instant features, structures, or characteristics as describedthroughout this specification may be combined in any suitable manner inone or more embodiments. For example, the usage of the phrases “exampleembodiments”, “some embodiments”, or other similar language, throughoutthis specification refers to the fact that a particular feature,structure, or characteristic described in connection with the embodimentmay be included in at least one embodiment. Thus, appearances of thephrases “example embodiments”, “in some embodiments”, “in otherembodiments”, or other similar language, throughout this specificationdo not necessarily all refer to the same group of embodiments, and thedescribed features, structures, or characteristics may be combined inany suitable manner in one or more embodiments.

In addition, while the term “message” may have been used in thedescription of embodiments, the application may be applied to many typesof network data, such as, packet, frame, datagram, etc. The term“message” also includes packet, frame, datagram, and any equivalentsthereof. Furthermore, while certain types of messages and signaling maybe depicted in exemplary embodiments they are not limited to a certaintype of message, and the application is not limited to a certain type ofsignaling.

Disclosed embodiments provide methods, systems, components,non-transitory computer readable media, devices, and/or networks, whichprovide for a Universal Identification Verification system (UIVS) thatcovers individuals, IoT devices, supply chain of electronics, etc.

In one embodiment, veryfID and DsTC proprietary application are used toscan all IDs of users in any country using a supported API. The userencrypted profiles attributes including DNA or UWA number may be sent toa proprietary database with the right policies for access. Verifiablecredentials and other attributes of the user profile may be turned intoan intermediate representation. In one embodiment, a digital phone bookor Digital Data Nucleic Authority (DDNA) may be created on a portalveryfID.name for the entire world to see whose ID is genuine based ontheir country and interests.

Power exchange and commerce using this ID solve ware with a distributedledger technology (DLT) or a blockchain may be used for implementinginteroperation. For example, if a user wants to send anything tosomeone, the user can just look up a target person by a phone number oran email address in the DDNA to get the exchange mode (e.g., M3UWA) aswell as a unique QR code to adopt the needed details to send money orshare things with the target person. Since anything is now possible onthe Internet, it is critical for a user to know who he is dealing withon another end of communications. The disclosed embodiments,advantageously, solve identification issues by interfacing a userdevice, a VC, a person and an advanced authentication.

The proposed universal system for verification of identity may employthe following:

Decentralized sTrueDid for communication (DsTC) and distributed ledgersystem for e-transactions (DLSeT). The DLSeT platform can include aserverless operating system with both public, private and consortiumdistributed ledgers that utilize a Lattice Face Secret KeyInfrastructure (LFSKI) feature that is distinct to the platform.

The DLSeT platform, employing a secret key infrastructure (SKI), canrealize advantages over many existing blockchain platforms based on apublic key infrastructure (PKI), being able to deliver safe andefficient transactions in a decentralized manner. The DLSeT platformincludes a distributed ledger, which maintains secure, and immutablerecords of all transactions conducted on the platform.

The distributed ledger can be configured, at least partially, as acryptographic infrastructure in a blockchain network. This allows thedistributed ledger aspects of the DLSeT platform to act as an encryptedstorage enclave for e-transactions. Furthermore, the DLSeT platformutilizes a user's attributes of users that typically does not changeoften over time (e.g., biometric data, driver license number, etc.) thatcan be further used to create an encrypted and unique Data NucleusAggregator (DNA) for the user. It is a user's DNA that is employedduring e-transactions on the DLSeT platform, providing a layer ofanonymity and added security for users. By collecting a plurality ofdifferent DNAs corresponding to different users, the DLSeT platformcreates a silo of the DDNA for its nodes.

The data of the DDNA serves as the building block for implementingLFSKI. Nodes participating in e-transactions via the DLSeT platform useLFSKI, which requires no private of public keys that are susceptible tohackers and other security. Thus, the DLSeT platform using LFSKIrealizes privacy, security (e.g., encryption 2048 bits), quantumcomputing resistance and a secure data life cycle. Also, the DLSeTplatform can utilize a consensus protocol, namely a prove of simpleuniverse wallet address (Po(SuA)), which allows only authorized users ofthe platform to securely transact. Moreover, the DLSeT platform may beconfigured to allow each user to identify themselves prior to aninteraction, with use of a Zero Knowledge Triangle Flow (ZT-Flow)protocol. The ZT-Flow protocol allows the platform to have a trustlessframework, where each user involved in a transaction can be identifiedwhile performing financial transactions, legitimately with integrity andconfidentiality. In addition, the DLSeT platform is configured to use adata life cycle security (DLCs). The DLCs allows users to control theirown data, for instance deciding when to monetize their data, or end thelife cycle of their data, as desired. The DLCs ensures that only usersinvolved in the transaction can share the data, or have the capabilityto access their owned data. Accordingly, no other party is allowed to beinvolved in, or impart a decision on, in the life of the data.

In one or more embodiments, the current Lattice face keylessinfrastructure (LFKI) may be implemented as follows: Lattice facekeyless infrastructure (LFKI) permeates a browser engine that usesidentity components for securing information by encrypted verification,validation, and evaluation via ECSMID. A decentralized application witha decentralized security is created, all entities requiringauthentication no longer must, reuse, move, store, and manage keys. Thismakes it highly possible to create a browser to uphold protocols likeECSMID, Zero-Trust, Zero-knowledge Flow, sTrueDID, UWA into a singledecentralization application called AFA browser with support to client(nodes) and server (nodes). All entities in the keyless infrastructurecan exist as standalones while retaining autonomy over their data. Thishas a high potential of preserving privacy and securing all informationon the internet. Encrypted searches (homomorphic encryption) could bedone via keywords. Resulting output could be decrypted following anexchange mechanism of batter, biding and prefixed pricing for any PII(biographic and demographic data).—These are the necessary component ofwhat we call Cyberlockx (AFA) browser on the internet.

The disclosed UIVS may use policies-permissions-roles and name and UWAverification. An artificial intelligence/machine learning (AI/ML) modulemay be used for generation of the intermediate representation.

The disclosed embodiments formulate conversion of physical object intointermediate representation in the digital space. This creates immutablerecord using cryptography from ECSMID disclosed in the U.S. Pat. No.10,911,217 B1. The template of policies defining user roles may beemployed. A portal where users can verify name, UWA and other datanucleus aggregates is provided. This establishes unique identifiers foreFRI or digital finger prints then notifies the users if something goeswrong with each DNA.

According to one embodiment, a user can verify a name from ID and viceversa meaning the user can verify the ID from the name itself. Forexample, if there is a portal with intermediate representations (QR codeor any other string that connect the verifiable credential to theperson), the user can check the name of a person whether it is realusing the portal. These credentials are public, but they are presentedin a format that does not reveal anything online except for those thatneeded and are authorized to access it.

FIG. 1 illustrates a network diagram of a system 100 including entitiesrequiring ID verification and an identification verification node,according to disclosed embodiments.

Referring to FIG. 1 , an identification verification node 102 may beconnected to entities requiring ID verification over a network. Theseentities may be a web server 101, a user smartphone (or tablet) 103, apersonal computer 105, a car 106 or any IoT device (not shown).

In one embodiment, the identification verification node 102 may beconnected to a database 108. In one embodiment, the UIVS database 108may be a ledger of a blockchain 113. The identification verificationnode 102 may reside on a cloud. As discussed above, the distributedledger 108 may be used for e-transactions DLSeT system.

In one embodiment, the identification verification node 102 may hostDsTC and DLSet modules and may implement polices, permissions and rolesof users and parties requesting verification. As discussed above, theidentification verification node 102 may be configured to use keylessencryption. The identification verification node 102 may be configuredto create immutable record using cryptography from ECSMID disclosed inthe U.S. Pat. 10,911,217 B1. The template(s) of policies defining userroles may be stored on the UIVS database ledger DB 108. Theidentification verification node 102 may provide a portal where userscan verify name, UWA and other data nucleus aggregates. Theidentification verification node 102 may establish unique identifiersfor eFRI or digital finger prints and may send notifications to theusers if something goes wrong with each DNA.

FIG. 2 illustrates a UIVS architecture 200, according to the disclosedembodiments.

Referring to FIG. 2 , UIVS architecture includes DsTC module 220 andDLSet module 221. The DsTc may use two user profiles—profile-a (201) andprofile-b (211). Each of the profiles may have respective SMS, texts(205 and 215). Each of the profiles 201 and 211 may have associatedaudio, video, picture data (207 and 217 respectively). The profiles 201and 211 may have associated UWA Ms 204 and 214. MsUWA data 206 and 216may be used to generate DNA M3 UWA (208 and 218 respectively). Localencrypted messages of profiles (209 and 219) are recorded as localencrypted messages sent to profile-a by profile-b (223) and as localencrypted messages sent to profile-b by profile-a (227) on DLSeT module.The DDNA 225 may be connected to the local encrypted messages ofprofile-a and profile-b (209 and 219). The verification process 229 maybe then implemented to verify user names based on the IDs or vice versausing encrypted profiles including DNA or UWA number stored in the UIVSdatabase with the right policies for access. The intermediaterepresentation such as a QR code 228 may be generated and used forverification of the IDs. The QR code may connect the verifiablecredential to the person. It may be used to check the name of a personto verify if it is real.

FIG. 2A illustrates a user interface that may be used with the UIVSarchitecture, according to the disclosed embodiments.

Referring to FIG. 2A, UIVS architecture includes a user interface 230that is connected to the system 200 in FIG. 2 . As discussed above, theverification process 229 may be then implemented to verify user namesbased on the IDs or vice versa using encrypted profiles including DNA orUWA number stored in the UIVS database 108 (FIG. 1 ) with the rightpolicies for access. The intermediate representation such as a QR code228 may be generated and used for verification of the IDs. The QR codemay connect the verifiable credential to the person. It may be used tocheck the name of a person to verify if it is real.

The user may enter data via the interface 230. The data may beassociated with categories such as what you know (WYK), what you have(WYH), what you are (WAY) and where you are (WrYA). The user can enterattributes such as Driver License (or another valid ID) information. Theuser can enter age restrictions and true or false conditions for IDauthenticity. The user can also set local restrictions for DNA and DDNA.

For example, in case of verification of a car identification, aregistration document back and front may be scanned. For example, carVIN # image may be used. Then, car front and back license plate imagesshowing the car may be used. Images of the car sides—passenger anddriver side showing full doors and body may be used. Owner name may beextracted and matched with the VIN # on in the image.

Then, all to documents including images of the car, name on the DL andon the car registration may be linked. The contact name on the DL and onthe registration are used to create car UWA. The 45 digit longalphanumeric special character string that start with capital letter LCNis generated. The string may be, for example:

4DOM+Vin#+InitialFLname+Plate#+Last5NumbersIMEI+Last7Address(googleopen).

Then, a shadow of the string is created. The payload functions, path, aQR code with a specific policy may be included. The authenticationverification node may send the stripped shadow UWA to client. The clientmay use 11 chars of the 42 each time get or post/request to the serverto perform a mutual authentication. Then, the server decrypts shadow UWAM6 to M5 to make certain it was not tampered with (i.e., it comes from acorrect server). Otherwise, the exchange or authorization will nothappen or will not be honored.

After authentication, the car generated QR code could be used tointeract with other devices, such as a smartphone which has its ownexchange identifier M3UWA or M3PIN as discussed in ECSMID described inthe U.S. Pat. No. 10,911,217 B1.

In one embodiment, a pre-arranged access control may be used based onthe policy and advanced authentication of data submitted by the user.Once the user is logged in, he may follow the advanced authentication tocomplete his tasks. For example, a user who logged in with only a username and password may not have the same privileges with another user whologged in with a user name, password and PIN or verified ID data. In oneembodiment, based on the registration attributes supplied by a user, theuser may have a set of privileges with permissions based on the profileattributes. This allows for efficient access control and accessmanagement. The user roles may be affected by the policies of the UIVSin accordance to the embodiments of the present invention.

FIG. 3 illustrates an example network including details of the IDverification server node, in accordance with embodiments of the presentinvention.

Referring to FIG. 3 , the example network 300 includes the IDverification node 102 connected to a web server node 101 over a network.Other nodes such the ones depicted in FIG. 1 may be connected to the IDverification node 102. The ID verification node 102 may host the UIVSsystem including DsTC module and DLSet module depicted in FIG. 2 anddiscussed above. The ID verification node 102 may be configured toreceive data from user interface 230 depicted in FIG. 2A. As discussedabove, the ID verification node 102 may invoke veryfID and DsTCproprietary application to scan all IDs of users in any country using asupported API. The user encrypted profiles attributes including DNA orUWA number may be sent to a proprietary database or ledger with theright policies for access. Verifiable credentials and other attributesof the user profile may be turned into an intermediate representation.In one embodiment, a digital phone book or Digital Data NucleicAuthority (DDNA) may be created on a portal veryfID.name for the entireworld to see whose ID is genuine based on their country and interests.

The ID verification node 102 may be a computing device or a servercomputer, or the like, and may include a processor 304, which may be asemiconductor-based microprocessor, a central processing unit (CPU), anapplication specific integrated circuit (ASIC), a field-programmablegate array (FPGA), and/or another hardware device. Although a singleprocessor 304 is depicted, it should be understood that the IDverification node 102 may include multiple processors, multiple cores,or the like, without departing from the scope of the ID verificationnode 102 system.

The ID verification node 102 may also include a non-transitory computerreadable medium 312 that may have stored thereon machine-readableinstructions executable by the processor 304. Examples of themachine-readable instructions are shown as 314-322 and are furtherdiscussed below. Examples of the non-transitory computer readable medium312 may include an electronic, magnetic, optical, or other physicalstorage device that contains or stores executable instructions. Forexample, the non-transitory computer readable medium 312 may be aRandom-Access memory (RAM), an Electrically Erasable ProgrammableRead-Only Memory (EEPROM), a hard disk, an optical disc, or other typeof storage device.

The processor 304 may fetch, decode, and execute the machine-readableinstructions 314 to acquire verifiable ID scan image data of all userswithin a country of residence. The processor 304 may fetch, decode, andexecute the machine-readable instructions 316 to receive users' profiledata. The processor 304 may fetch, decode, and execute themachine-readable instructions 318 to generate encrypted user profileattributes comprising DNA. The processor 304 may fetch, decode, andexecute the machine-readable instructions 320 to execute a transactionto store the encrypted user profiles on a ledger along withcorresponding access policies. The processor 304 may fetch, decode, andexecute the machine-readable instructions 322 to generate anintermediate representation for each user based on the verifiable IDscan image data and the encrypted user profile attributes.

FIG. 4A illustrates a flow diagram 450 of an example method, accordingto disclosed embodiments. FIG. 4A illustrates a flow chart of an examplemethod executed by the ID verification node 102 (see FIG. 1 ). It shouldbe understood that the method 450 depicted in FIG. 4A may includeadditional operations and that some of the operations described thereinmay be removed and/or modified without departing from the scope of themethod 450. The description of the method 450 is also made withreference to the features depicted in FIG. 3 for purposes ofillustration. Particularly, the processor 304 of the ID verificationnode 102 may execute some or all of the operations included in themethod 450.

Referring to FIG. 4A, the method 450 may also include one or more of thefollowing steps. At block 452, the processor 304 may acquire verifiableID scan image data of all users within a country of residence. At block454, the processor 304 may receive users' profile data. At block 456,the processor 304 may generate encrypted user profile attributescomprising DNA. At block 458, the processor 304 may execute atransaction to store the encrypted user profiles on a ledger along withcorresponding access policies. At block 460, the processor 304 maygenerate an intermediate representation for each user based on theverifiable ID scan image data and the encrypted user profile attributes.

FIG. 4B illustrates a network 480 used for the Universal IdentificationVerification System including AI module for predictive inputs, inaccordance with embodiments of the present invention.

As discussed above, an artificial intelligence/machine learning (AI/ML)module may be used for generation of the intermediate representation.

The intermediate representation (e.g., QR code) may be obtained by usingpredictive data analytics from an AI module 412 that compares user storeuser profile data and previously verified credentials. The AI module 412may be executed on the ID verification node 102 or may reside on a cloudserver node 408. The ID verification node 102 may use locally storeduser profile attributes as well. The AI module 412 may generatepredictive analytics model 413 which may process, for example, profiledata provided by the UIVS. The analytical data may be stored on a ledgerof a blockchain as a reliable audible log. While the AI module 412 mayuse data acquired form neural networks, it may also use someheuristics-related data stored on the ledger for predictive analytics.

The above embodiments may be implemented in hardware, in a computerprogram executed by a processor, in firmware, or in a combination of theabove. A computer program may be embodied on a computer readable medium,such as a storage medium. For example, a computer program may reside inrandom access memory (“RAM”), flash memory, read-only memory (“ROM”),erasable programmable read-only memory (“EPROM”), electrically erasableprogrammable read-only memory (“EEPROM”), registers, hard disk, aremovable disk, a compact disk read-only memory (“CD-ROM”), or any otherform of storage medium known in the art.

An exemplary storage medium may be coupled to the processor such thatthe processor may read information from, and write information to, thestorage medium. In the alternative, the storage medium may be integralto the processor. The processor and the storage medium may reside in anapplication specific integrated circuit (“ASIC”). In the alternative,the processor and the storage medium may reside as discrete components.For example, FIG. 5 illustrates an example computer system/server node500, which may represent or be integrated in any of the above-describedcomponents, etc.

FIG. 5 is not intended to suggest any limitation as to the scope of useor functionality of embodiments of the application described herein.Regardless, the computing node 500 is capable of being implementedand/or performing any of the functionality set forth hereinabove.

In the computing node 500 there is a computer system/server 502, whichis operational with numerous other general purposes or special purposecomputing system environments or configurations. Examples of well-knowncomputing systems, environments, and/or configurations that may besuitable for use with computer system/server 502 include, but are notlimited to, personal computer systems, server computer systems, thinclients, thick clients, hand-held or laptop devices, multiprocessorsystems, microprocessor-based systems, set top boxes, programmableconsumer electronics, network PCs, minicomputer systems, mainframecomputer systems, and distributed cloud computing environments thatinclude any of the above systems or devices, and the like.

Computer system/server 502 may be described in the general context ofcomputer system-executable instructions, such as program modules, beingexecuted by a computer system. Generally, program modules may includeroutines, programs, objects, components, logic, data structures, and soon that perform particular tasks or implement particular abstract datatypes. Computer system/server 502 may be practiced in distributed cloudcomputing environments where tasks are performed by remote processingdevices that are linked through a communications network. In adistributed cloud computing environment, program modules may be locatedin both local and remote computer system storage media including memorystorage devices.

As shown in FIG. 5 , the computer system/server 502 may be used in cloudcomputing node 900 shown in the form of a general-purpose computingdevice. The components of the computer system/server 502 may include,but are not limited to, one or more processors or processing units 504,a system memory 506, and a bus that couples various system componentsincluding system memory 506 to processor 504.

The bus represents one or more of any of several types of busstructures, including a memory bus or memory controller, a peripheralbus, an accelerated graphics port, and a processor or local bus usingany of a variety of bus architectures. By way of example, and notlimitation, such architectures include Industry Standard Architecture(ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA)bus, Video Electronics Standards Association (VESA) local bus, andPeripheral Component Interconnects (PCI) bus.

The exemplary computer system/server 502 typically includes a variety ofcomputer system readable media. Such media may be any available mediathat is accessible by the computer system/server 502, and it includesboth volatile and non-volatile media, removable and non-removable media.System memory 506, in one embodiment, implements the flow diagrams ofthe other figures. The system memory 506 can include computer systemreadable media in the form of volatile memory, such as random-accessmemory (RAM) 510 and/or cache memory 512. The computer system/server 502may further include other removable/non-removable, volatile/non-volatilecomputer system storage media. By way of example only, storage system514 can be provided for reading from and writing to a non-removable,non-volatile magnetic media (not shown and typically called a “harddrive”). Although not shown, a magnetic disk drive for reading from andwriting to a removable, non-volatile magnetic disk, and an optical diskdrive for reading from or writing to a removable, non-volatile opticaldisk such as a CD-ROM, DVD-ROM or other optical media can be provided.In such instances, each can be connected to the bus by one or more datamedia interfaces. As will be further depicted and described below,memory 906 may include at least one program product having a set (e.g.,at least one) of program modules that are configured to carry out thefunctions of various embodiments of the application.

Program/utility 516, having a set (at least one) of program modules 518,may be stored in memory 506 by way of example, and not limitation, aswell as an operating system, one or more application programs, otherprogram modules, and program data. Each of the operating system, one ormore application programs, other program modules, and program data orsome combination thereof, may include an implementation of a networkingenvironment. Program modules 518 generally carry out the functionsand/or methodologies of various embodiments of the application asdescribed herein.

As will be appreciated by one skilled in the art, aspects of the presentapplication may be embodied as a system, method, or computer programproduct. Accordingly, aspects of the present application may take theform of an entirely hardware embodiment, an entirely software embodiment(including firmware, resident software, micro-code, etc.) or anembodiment combining software and hardware aspects that may allgenerally be referred to herein as a “circuit,” “module” or “system.”Furthermore, aspects of the present application may take the form of acomputer program product embodied in one or more computer readablemedium(s) having computer readable program code embodied thereon.

The computer system/server 502 may also communicate with one or moreexternal devices 520 such as a keyboard, a pointing device, a display522, etc.; one or more devices that enable a user to interact withcomputer system/server 502; and/or any devices (e.g., network card,modem, etc.) that enable computer system/server 502 to communicate withone or more other computing devices. Such communication can occur viaI/O interfaces 524. Still yet, the computer system/server 502 cancommunicate with one or more networks such as a local area network(LAN), a general wide area network (WAN), and/or a public network (e.g.,the Internet) via network adapter 526. As depicted, network adapter 526communicates with the other components of computer system/server 502 viaa bus. It should be understood that although not shown, other hardwareand/or software components could be used in conjunction with computersystem/server 502. Examples include, but are not limited to: microcode,device drivers, redundant processing units, external disk drive arrays,RAID systems, tape drives, and data archival storage systems, etc.

Although an embodiment of at least one of a system, method, andnon-transitory computer readable medium has been illustrated in theaccompanied drawings and described in the foregoing detaileddescription, it will be understood that the application is not limitedto the embodiments disclosed, but is capable of numerous rearrangements,modifications, and substitutions as set forth and defined by thefollowing claims. For example, the capabilities of the system of thevarious figures can be performed by one or more of the modules orcomponents described herein or in a distributed architecture and mayinclude a transmitter, recipient or pair of both. For example, all orpart of the functionality performed by the individual modules, may beperformed by one or more of these modules. Further, the functionalitydescribed herein may be performed at various times and in relation tovarious events, internal or external to the modules or components. Also,the information sent between various modules can be sent between themodules via at least one of: a data network, the Internet, a voicenetwork, an Internet Protocol network, a wireless device, a wired deviceand/or via plurality of protocols. Also, the messages sent or receivedby any of the modules may be sent or received directly and/or via one ormore of the other modules.

One skilled in the art will appreciate that a “system” could be embodiedas a personal computer, a server, a console, a personal digitalassistant (PDA), a cell phone, a tablet computing device, a Smart phoneor any other suitable computing device, or combination of devices.Presenting the above-described functions as being performed by a“system” is not intended to limit the scope of the present applicationin any way but is intended to provide one example of many embodiments.Indeed, methods, systems and apparatuses disclosed herein may beimplemented in localized and distributed forms consistent with computingtechnology.

It should be noted that some of the system features described in thisspecification have been presented as modules, in order to moreparticularly emphasize their implementation independence. For example, amodule may be implemented as a hardware circuit comprising custom verylarge-scale integration (VLSI) circuits or gate arrays, off-the-shelfsemiconductors such as logic chips, transistors, or other discretecomponents. A module may also be implemented in programmable hardwaredevices such as field programmable gate arrays, programmable arraylogic, programmable logic devices, graphics processing units, or thelike.

A module may also be at least partially implemented in software forexecution by various types of processors. An identified unit ofexecutable code may, for instance, comprise one or more physical orlogical blocks of computer instructions that may, for instance, beorganized as an object, procedure, or function. Nevertheless, theexecutables of an identified module need not be physically locatedtogether but may comprise disparate instructions stored in differentlocations which, when joined logically together, comprise the module andachieve the stated purpose for the module. Further, modules may bestored on a computer-readable medium, which may be, for instance, a harddisk drive, flash device, random access memory (RAM), tape, or any othersuch medium used to store data.

Indeed, a module of executable code could be a single instruction, ormany instructions, and may even be distributed over several differentcode segments, among different programs, and across several memorydevices. Similarly, operational data may be identified and illustratedherein within modules and may be embodied in any suitable form andorganized within any suitable type of data structure. The operationaldata may be collected as a single data set or may be distributed overdifferent locations including over different storage devices, and mayexist, at least partially, merely as electronic signals on a system ornetwork.

It will be readily understood that the components of the application, asgenerally described and illustrated in the figures herein, may bearranged and designed in a wide variety of different configurations.Thus, the detailed description of the embodiments is not intended tolimit the scope of the application as claimed but is merelyrepresentative of selected embodiments of the application.

One having ordinary skill in the art will readily understand that theabove may be practiced with steps in a different order, and/or withhardware elements in configurations that are different than those whichare disclosed. Therefore, although the application has been describedbased upon these preferred embodiments, it would be apparent to those ofskill in the art that certain modifications, variations, and alternativeconstructions would be apparent.

While preferred embodiments of the present application have beendescribed, it is to be understood that the embodiments described areillustrative only and the scope of the application is to be definedsolely by the appended claims when considered with a full range ofequivalents and modifications (e.g., protocols, hardware devices,software platforms, etc.) thereto.

What is claimed is:
 1. A system, comprising: a processor of an IDverification node connected to at least one node over a network; amemory on which are stored machine-readable instructions that whenexecuted by the processor, cause the processor to: acquire verifiable IDscan image data of all users within a country of residence; receiveusers' profile data; generate encrypted user profile attributescomprising DNA; execute a transaction to store the encrypted userprofiles on a ledger along with corresponding access policies; andgenerate an intermediate representation for each user based on theverifiable ID scan image data and the encrypted user profile attributes.2. The system of claim 1, wherein the instructions further cause theprocessor to generate a Digital Data Nucleic Authority (DDNA) to exposethe user IDs that are genuine based on their country of residence. 3.The system of claim 1, wherein the instructions further cause theprocessor to generate encrypted user profile attributes including UWAnumbers generated based on users' profile data.
 4. The system of claim1, wherein the instructions further cause the processor to extract username from a profile to be matched with a user name of the verifiable IDscan image data.
 5. The system of claim 1, wherein the instructionsfurther cause the processor to generate an alphanumeric specialcharacter string based on user profile data and to generate a shadowstring of the alphanumeric special character string.
 6. The system ofclaim 5, wherein the shadow string includes in intermediaterepresentation comprising QR code with a specified access policy.
 7. Thesystem of claim 5, wherein the instructions further cause the processorto generate a stripped shadow UWA and to send the stripped shadow UWA toa client, wherein the client performs a mutual authentication by using asubset of characters to get or post a request to the ID verificationnode.
 8. The system of claim 7, wherein the instructions further causethe processor to decrypt shadow UWA M6 to M5 to confirm that the UWA hasnot been tampered with.
 9. A method, comprising: acquiring, by an IDverification node, a verifiable ID scan image data of all users within acountry of residence; receiving, by the ID verification node, users'profile data; generating, by the ID verification node, encrypted userprofile attributes comprising DNA; executing, by the ID verificationnode, a transaction to store the encrypted user profiles on a ledgeralong with corresponding access policies; and generating an intermediaterepresentation for each user based on the verifiable ID scan image dataand the encrypted user profile attributes.
 10. The method of claim 9,further comprising generating a Digital Data Nucleic Authority (DDNA) toexpose the user IDs that are genuine based on their country ofresidence.
 11. The method of claim 9, further comprising generatingencrypted user profile attributes including UWA numbers generated basedon users' profile data.
 12. The method of claim 9, further comprisingextracting user name from a profile to be matched with a user name ofthe verifiable ID scan image data.
 13. The method of claim 9, furthercomprising generating an alphanumeric special character string based onuser profile data and to generate a shadow string of the alphanumericspecial character string.
 14. The method of claim 13, wherein the shadowstring includes in intermediate representation comprising QR code with aspecified access policy.
 15. The method of claim 13, further comprisinggenerating a stripped shadow UWA and sending the stripped shadow UWA toa client, wherein the client performs a mutual authentication by using asubset of characters to get or post a request to the ID verificationnode.
 16. The method of claim 15, further comprising decrypt shadow UWAM6 to M5 to confirm that the UWA has not been tampered with.
 17. Anon-transitory computer readable medium comprising instructions, thatwhen read by a processor, cause the processor to perform: acquiring averifiable ID scan image data of all users within a country ofresidence; receiving users' profile data; generating encrypted userprofile attributes comprising DNA; executing a transaction to store theencrypted user profiles on a ledger along with corresponding accesspolicies; and generating an intermediate representation for each userbased on the verifiable ID scan image data and the encrypted userprofile attributes.
 18. The non-transitory computer readable medium ofclaim 17, further comprising instructions, that when read by theprocessor, cause the processor to generate a Digital Data NucleicAuthority (DDNA) to expose the user IDs that are genuine based on theircountry of residence.
 19. The non-transitory computer readable medium ofclaim 17, further comprising instructions, that when read by theprocessor, cause the processor to generate encrypted user profileattributes including UWA numbers generated based on users' profile data.20. The non-transitory computer readable medium of claim 17, furthercomprising instructions, that when read by the processor, cause theprocessor to extract a first username from a profile to be matched witha second username of the verifiable ID scan image data.